Skip to content

Conversation

@wesleywiser
Copy link
Member

Fixes a bunch of warnings that are generated during the stage0 build of libcollections.

@rust-highfive
Copy link
Contributor

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

@Gankra
Copy link
Contributor

Gankra commented May 31, 2015

Hmm, is this the sort of thing that needs to hang around forever, or is just pending a new snapshot?

@wesleywiser
Copy link
Member Author

@gankro I'm not sure. Sorry, I'm new to working on rust. What's the effect of taking a new snapshot?

@Gankra
Copy link
Contributor

Gankra commented May 31, 2015

Stage0 is building the current source from a snapshot binary build of the source from a while back. This often means stage0 has to do some trippy stuff to bridge the gap between today's and yesterday's Rust. Taking a new snapshot makes the gap smaller and thus reduces the amount of conditional things the source needs to include to handle this. If this doesn't pop up in stage1 or 2 I assume that's the problem, but since 1.0 I haven't kept up on what the snapshot "process" is.

@Gankra Gankra added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label May 31, 2015
@Gankra
Copy link
Contributor

Gankra commented May 31, 2015

Basically I like the idea of cleaning up the output, but not if it's just making more work for a temporary thing. We're doing triage tomorrow, and I'll look into what's up with this then.

Thanks for the contribution, though!

@wesleywiser
Copy link
Member Author

Sure. Thanks for the explanation! I initially only noticed the warnings
during stage0 so I'm not sure if they also occur in later stages. If they
don't, I assume this is a non issue then?

On Sun, May 31, 2015, 6:53 PM Alexis Beingessner [email protected]
wrote:

Basically I like the idea of cleaning up the output, but not if it's just
making more work for a temporary thing. We're doing triage tomorrow, and
I'll look into what's up with this then.

Thanks for the contribution, though!


Reply to this email directly or view it on GitHub
#25935 (comment).

@alexcrichton
Copy link
Member

I think this isn't related to the stage0 build but rather unit tests (which means that these need to stick around for awhile), just to clarify! I'll add a few comments inline.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you move this down near the other cfg_attr features?

@wesleywiser wesleywiser force-pushed the fix_libcollection_build_warnings branch from 4d751b7 to 558491c Compare June 1, 2015 23:06
@wesleywiser
Copy link
Member Author

@alexcrichton Thanks for the feedback! I've pushed a new commit with your suggestions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Conventionally we have a space after the last slash (e.g. // foo)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, sorry

@wesleywiser wesleywiser force-pushed the fix_libcollection_build_warnings branch from 558491c to 99df383 Compare June 1, 2015 23:32
@wesleywiser
Copy link
Member Author

@alexcrichton Fixed. Thanks!

@alexcrichton
Copy link
Member

@bors: r+ 99df383

@bors
Copy link
Collaborator

bors commented Jun 3, 2015

⌛ Testing commit 99df383 with merge 2c8d75d...

bors added a commit that referenced this pull request Jun 3, 2015
…r=alexcrichton

Fixes a bunch of warnings that are generated during the stage0 build of libcollections.
@bors bors merged commit 99df383 into rust-lang:master Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants